GH-4089 Fixed the issue where sensitive words in chat memory repeatedly triggered SafeGuardAdvisor interception #4112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described in the issue, the current default order of
SafeGuardAdvisor
is lower than that ofMessageChatMemoryAdvisor
, which causes a problem: when users employ both advisors simultaneously without manually adjusting theirorder
, if any historical message contains sensitive content, all subsequent messages will be blocked bySafeGuardAdvisor
. This behavior is clearly undesirable.This PR addresses the issue with the following changes:
SafeGuardAdvisor
to be higher than that ofMessageChatMemoryAdvisor
, ensuring that content filtering occurs before chat memory is stored.SafeGuardAdvisor
to alert users about this potential issue and recommend appropriate priority configuration based on their specific use cases.Fixes: #4089